Split GitHub integration into Cloud Security and Code Security; document permissions update for Code Security #38
Conversation
…ent permissions update for Code Security
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughAdds a new GitHub (Code Security) documentation page and renames/updates the existing GitHub page to GitHub (Cloud Security), refining setup text, permission scopes, monitored resources, adding a Common Issues entry, and noting an update (2025-11-03) about upcoming CI check support and permission changes. Changes
Sequence Diagram(s)sequenceDiagram
participant User as GitHub User / PR
participant GitHub as GitHub API
participant Service as Cloud/Code Security Integration
participant CI as CI checks
rect rgb(235,245,255)
Note over User,Service: New CI check support (2025-11-03)
end
User->>GitHub: Open PR / push commit
GitHub->>Service: Webhook (pull_request / check_run) [requires Checks & PR scopes]
alt CI check enabled
Service->>CI: Trigger/validate Code Security check
CI->>GitHub: Report check status
GitHub->>Service: Check result callback
else CI not used
Service->>GitHub: Read PR metadata / contents (requires metadata/contents scopes)
end
Service->>User: Surface findings / statuses in UI
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro Knowledge base: Disabled due to 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting
📒 Files selected for processing (2)
pages/integrations/github-code-security.mdx(1 hunks)pages/integrations/github.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
pages/integrations/github.mdx
[grammar] ~17-~17: There might be a mistake here.
Context: ... on GitHub: - Repository administration - Repository Dependabot alerts - Repositor...
(QB_NEW_EN)
[grammar] ~18-~18: There might be a mistake here.
Context: ...istration - Repository Dependabot alerts - Repository metadata - Repository webhook...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ... Dependabot alerts - Repository metadata - Repository webhooks - Organization admin...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ...epository metadata - Repository webhooks - Organization administration - Organizati...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...y webhooks - Organization administration - Organization members - Organization webh...
(QB_NEW_EN)
[grammar] ~22-~22: There might be a mistake here.
Context: ...on administration - Organization members - Organization webhooks ### Which resourc...
(QB_NEW_EN)
[grammar] ~29-~29: There might be a mistake here.
Context: ...he following on GitHub: - Organizations - Repositories - Branch protection rules...
(QB_NEW_EN)
[grammar] ~30-~30: There might be a mistake here.
Context: ... GitHub: - Organizations - Repositories - Branch protection rules - Dependabot a...
(QB_NEW_EN)
[grammar] ~31-~31: There might be a mistake here.
Context: ...Repositories - Branch protection rules - Dependabot alerts ## Common Issues ###...
(QB_NEW_EN)
pages/integrations/github-code-security.mdx
[grammar] ~17-~17: There might be a mistake here.
Context: ...on GitHub: - Repository metadata (read) - Repository contents (read) - Repository ...
(QB_NEW_EN)
[grammar] ~18-~18: There might be a mistake here.
Context: ...data (read) - Repository contents (read) - Repository checks (read and write) - Rep...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ...ad) - Repository checks (read and write) - Repository pull requests (read and write...
(QB_NEW_EN)
[grammar] ~32-~32: There might be a mistake here.
Context: ...ite access to Checks on repositories - Read and write access to **Pull requests...
(QB_NEW_EN)
Problem
We need a permissions update for GitHub (Code Security) to enable PR checks.
Solution
Document it here.
I've also split out the two GitHub integrations for Cloud Security and Code Security, to match what we have on the platform. I left the slug as-is for Cloud Security to avoid breaking links.
Summary by CodeRabbit